Clarifications from the Edgeware team #7

thomivy · 2019-07-25T20:32:46Z

Typos, clarity, and language modifications

Typos, clarity, and language modicfications

chrishobcroft · 2019-07-26T17:41:10Z

faq.yaml

-        the lockdrop and centralizes the initial distribution. To ensure a balanced token model that is
-        both legitimate and inclusive of both lockdrop and signal participants, a number of distribution
-        improvements have been made prior to genesis.
+        the design of signalling in the EEdgeware lockdrop leads to many edge conditions that may hamper the optimal


Typo: "EEdgeware"

chrishobcroft · 2019-07-26T17:41:47Z

faq.yaml


        1. Remove Signalling on Behalf of Contracts

        2. Remove Generalized Locking

-        3. All signalled funds distributed in genesis
+        3.  All token allocations to signallers distributed fully at genesis.


Typo: Extra space between 3. and All

chrishobcroft · 2019-07-26T17:42:33Z

faq.yaml

@@ -54,33 +53,34 @@ en:
        msg.value greater than 0 for the entirety of the 3, 6 or 12-month lock durations”,
        and in these cases “that signal can be treated as a lock for the purposes of the allocation award”. 

-        By removing the ability to signal on behalf of a contract, Straightedge has solved for Generalized
-        Locks and other edge case vulnerabilities. However, it is still worth explicitly pointing out some
+        By removing the ability to signal on behalf of a contract, Straightedge has ntended to reduce vulnerabilities by


Typo: "ntended"

The point here was to say that, we that generalized locks are a moot point given that we "signalling on behalf of a contract" is removed. However, we want to share some reasons why the generalized lock is especially harmful, even more so than a normal "contract signal".

chrishobcroft · 2019-07-26T17:43:26Z

faq.yaml

        of the issues with the policy. First, it places undue burden upon the launchers of the network to
        audit and decide on different generalized lock contracts, which may contain edge cases such as
        bypassing locking by issuing derivatives of the locked Ether (such as with WETH). Further, if a
        contract does not correctly lock, or if code claiming to be a lock bypasses detection through
        underhanded Solidity techniques, it could break the legitimacy of the initial distribution of
-        the entire network. Removing generalized locking removes the necessity for case-by-case decision-making
-        by a launch-team, and other edge case vulnerabilities.
+        the entire network. While Edgeware’s contract codes have been fully audited by Quantstamp,  Removing generalized


Typo: unnecessary extra space between Quantstamp, and Removing

Typo: Removing should be without capital.

The Commonwealth-written contracts aren't relevant to this point. It's about new generalized lock contracts. Is Quantstamp going to audit all of those?

chrishobcroft · 2019-07-26T17:44:56Z

faq.yaml

-        provide a substantial voting-percentage of all network-tokens to a party or parties not in control
-        of the funds for which tokens are rewarded.
+        provide favor to several small, select group of individuals and teams. While the changes were disclosed before the
+        lockdrop began The result would provide an estimated 9% substantial voting-percentage of all network-tokens to a


Typo: "began The result" doesn't need a capital T

Challenge: how is this 9% calculated?

how is this 9% calculated?

++ @thomivy

chrishobcroft · 2019-07-26T17:46:13Z

faq.yaml

-        Please review the Edgeware FAQs where you can learn more about the lockdrop contracts,
-        the Straightedge software, and incentives for validation.
+        Since Straightedge is a new project and a fork, we rely upon the efforts of the Edgeware developers for our
+        documentatione At their site, https://edgewa.re, you can review the Edgeware FAQs where you can learn more about the


Typo: "documentatione At their site" - documentation doesn't need an extra e, and At doesn't need capital A

sunnya97 · 2019-07-28T13:27:06Z

faq.yaml

@@ -54,33 +53,34 @@ en:
        msg.value greater than 0 for the entirety of the 3, 6 or 12-month lock durations”,
        and in these cases “that signal can be treated as a lock for the purposes of the allocation award”. 

-        By removing the ability to signal on behalf of a contract, Straightedge has solved for Generalized


Suggested change

By removing the ability to signal on behalf of a contract, Straightedge has solved for Generalized

By removing the ability to signal on behalf of a contract, Straightedge has already removed the Generalized

sunnya97 · 2019-07-28T13:29:24Z

faq.yaml


        1. Remove Signalling on Behalf of Contracts

        2. Remove Generalized Locking

-        3. All signalled funds distributed in genesis
+        3.  All token allocations to signallers distributed fully at genesis.


Suggested change

3. All token allocations to signallers distributed fully at genesis.

3. All token allocations to signallers distributed fully at genesis.

sunnya97 · 2019-07-28T13:31:22Z

faq.yaml

@@ -115,14 +115,16 @@ en:

    - question: How are STR tokens distributed?
      answer: |
-        Lockdrop and signal participants will receive 90% of STR tokens, with the exception of contributions
-        through signalling on behalf of a contract. The remaining 10% of distribution will be allocated as
+        The proportions of the Straightedge genesis block distribution mirror the proportions of Edgeware Lockdrop and


Suggested change

The proportions of the Straightedge genesis block distribution mirror the proportions of Edgeware Lockdrop and

The proportions of the Straightedge genesis block distribution mirror the proportions of Edgeware Lockdrop in which

sunnya97 · 2019-07-28T13:31:31Z

faq.yaml

-        Lockdrop and signal participants will receive 90% of STR tokens, with the exception of contributions
-        through signalling on behalf of a contract. The remaining 10% of distribution will be allocated as
+        The proportions of the Straightedge genesis block distribution mirror the proportions of Edgeware Lockdrop and
+        signal participants will receive 90% of STR tokens, with the exception of contributions


Suggested change

signal participants will receive 90% of STR tokens, with the exception of contributions

lock and signal participants will receive 90% of STR tokens, with the exception of contributions

sunnya97 · 2019-07-28T13:32:29Z

faq.yaml

        a founders’ reward to entities contributing to the launch of the Straightedge project.

    - question: What if I want to learn more about the lockdrop or technical details?
      answer: |
-        Please review the Edgeware FAQs where you can learn more about the lockdrop contracts,
-        the Straightedge software, and incentives for validation.
+        Since Straightedge is a new project and a fork, we rely upon the efforts of the Edgeware developers for our


Suggested change

Since Straightedge is a new project and a fork, we rely upon the efforts of the Edgeware developers for our

As the Straightedge lockdrop is the same process as the Edgeware lockdrop, we recommend checking out the documentation written by the Edgeware development team

sunnya97 · 2019-07-28T13:36:12Z

faq.yaml

-        Please review the Edgeware FAQs where you can learn more about the lockdrop contracts,
-        the Straightedge software, and incentives for validation.
+        Since Straightedge is a new project and a fork, we rely upon the efforts of the Edgeware developers for our
+        documentatione At their site, https://edgewa.re, you can review the Edgeware FAQs where you can learn more about the


Suggested change

documentatione At their site, https://edgewa.re, you can review the Edgeware FAQs where you can learn more about the

available on their website, https://edgewa.re. There you can review the Edgeware FAQs where you can learn more about the

Clarifications from the Edgeware team

8efa39a

Typos, clarity, and language modicfications

chrishobcroft reviewed Jul 26, 2019

View reviewed changes

sunnya97 reviewed Jul 28, 2019

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Clarifications from the Edgeware team #7

Clarifications from the Edgeware team #7

thomivy commented Jul 25, 2019

chrishobcroft Jul 26, 2019

chrishobcroft Jul 26, 2019

chrishobcroft Jul 26, 2019

sunnya97 Jul 28, 2019

chrishobcroft Jul 26, 2019

sunnya97 Jul 28, 2019

chrishobcroft Jul 26, 2019

sunnya97 Jul 28, 2019 •

edited

Loading

chrishobcroft Jul 26, 2019

sunnya97 Jul 28, 2019

sunnya97 Jul 28, 2019

sunnya97 Jul 28, 2019

sunnya97 Jul 28, 2019

sunnya97 Jul 28, 2019

sunnya97 Jul 28, 2019

	By removing the ability to signal on behalf of a contract, Straightedge has solved for Generalized
	By removing the ability to signal on behalf of a contract, Straightedge has already removed the Generalized

	3. All token allocations to signallers distributed fully at genesis.
	3. All token allocations to signallers distributed fully at genesis.

	The proportions of the Straightedge genesis block distribution mirror the proportions of Edgeware Lockdrop and
	The proportions of the Straightedge genesis block distribution mirror the proportions of Edgeware Lockdrop in which

	signal participants will receive 90% of STR tokens, with the exception of contributions
	lock and signal participants will receive 90% of STR tokens, with the exception of contributions

	Since Straightedge is a new project and a fork, we rely upon the efforts of the Edgeware developers for our
	As the Straightedge lockdrop is the same process as the Edgeware lockdrop, we recommend checking out the documentation written by the Edgeware development team

	documentatione At their site, https://edgewa.re, you can review the Edgeware FAQs where you can learn more about the
	available on their website, https://edgewa.re. There you can review the Edgeware FAQs where you can learn more about the

Clarifications from the Edgeware team #7

Are you sure you want to change the base?

Clarifications from the Edgeware team #7

Conversation

thomivy commented Jul 25, 2019

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

sunnya97 Jul 28, 2019 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

sunnya97 Jul 28, 2019 •

edited

Loading